-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Update Agents dev docs to add MCP server page #19689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 files reviewed, 3 total issue(s) found.
Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
irvinebroque
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@geelen for 👀 and then let's ship it
Does feel like need some callout about being local only today, remote soon.
| ## Building an MCP Server on Cloudflare Workers | ||
|
|
||
| Normally, setting up an MCP server requires handling infrastructure, API routing, and understanding the MCP protocol. But with [Cloudflare Workers](/workers/), all the heavy lifting is done for you, so all you need to do is define your service's functionality. | ||
| Once deployed, your Worker becomes an MCP server that AI assistants (as long as they support MCP) can connect to and use to interact with your service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to caveat local only somewhere early?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are currently only local MCP clients, so it's not really necessary to specify right now. But as long as we update the workers-mcp package when remote MCP drops I think this documentation can stay unchanged?
Deploying cloudflare-docs with
|
| Latest commit: |
6c3dcb1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1daa0227.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://add-mcp-page.cloudflare-docs-7ou.pages.dev |
Co-authored-by: Brendan Irvine-Broque <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 files reviewed, 1 total issue(s) found.
Updated wrangler commands for installing wrangler and creating new worker
Added step 3 - configuring the worker to support MCP
small edit
Summary
Added a new page to the Agents documentation to show how customers how they can build an MCP server on Cloudflare Workers.
Screenshots (optional)
Documentation checklist